About: Item

This page provides a structured representation (serialized as HTML+RDFa) of the description of the entity denoted ("referred to") by the hyperlink that anchors the About: <Entity Label> text at the top.

The data is presented here in the form of a collection of Entity->Attribute->Value (EAV) or Subject->Predicate->Object (SPO) relations.

In conformance with core Web Architecture, the same description data may also be retrieved in a variety of other negotiable serialization formats, which currently include CSV, HTML+Microdata, (X)HTML+RDFa, N-Triples, Turtle, N3, RDF/JSON, JSON-LD, RDF/XML, Atom, and CXML.

Why is this page important?

This page and its neighbors provide 5-Star Linked Data URIs (Web Super Keys) for HTTP-accessible data. These URIs are powerful starting points for serendipitous data discovery using the Web's "follow your nose" pattern, as well as a key ingredient for SPARQL queries over HTTP, ODBC, JDBC, ADO.NET, OLE-DB, or XMLA connections.

A single link from this page can be the seed of a powerful Web traversal, en route to discovery and exploitation of unimagined insights, using existing tools such as browsers, spreadsheets, business intelligence and analytics packages, basic report writers, presentation generators, project management packages, and many others.

How can I discover more structured data like this?

A variety of discovery pointers are available to users and user agents (software programs) that include:

<link /> relations embedded within the <head /> section of each description page
"Link:" response headers included as part of HTTP response metadata.

Can I expose my own Web resources this way?

Yes! Simply include entries, based on the example below, in the <head/> section of your (X)HTML page, whether static or dynamically generated --

<link rel="related"
    title="My Data in Linked Data form"
    href="http://linkeddata.uriburner.com/about/id/<scheme-part-of-url>/<host-part-of-url>/<path-part-of-url>"
    />

The scheme part is the first bit of a URI, up to but not including the first colon (":"). The host part includes the port, if any, and is found between the double solidus ("//") following the first colon, and the first solidus ("/") thereafter. The path part is everything thereafter (possibly including a query part or fragment identifier part).

For example, if your original page were at --

http://en.wikipedia.org/wiki/Linked_Data

-- the scheme part is "http", the host part is "en.wikipedia.org", and the path part is "wiki/Linked_Data". You could therefore provide access to a Linked Data graph rendition by including a <head/> entry like this --

<link
    rel="related"
    title="Linked data - Wikipedia, the free encyclopedia - in Linked Data form"
    href="http://linkeddata.uriburner.com/about/id/http/en.wikipedia.org/wiki/Linked_Data"
    />

Additional Information

URIBurner.com -- a live service that produces pages like this
OpenLink Data Explorer (ODE) -- a browser plug-in that enables you to browse and bookmark Linked Data pages via additions to the browser menus, both main and contextual
- ODE usage examples

Sponging disallowed (Read-only view)

qrcode_icon

http://rdfs.org/sioc/ns#Item

An Item is something which can be in a Container.

% meta-cartridges called:

Meta-cartridge [execution time]:

Subject of Relation
Object of Relation

Property	Value
type	Classhttp://www.w3.org/2002/07/owl#Class
label	Item (en)
isDefinedBy	SIOC Core Ontology Namespacehttp://rdfs.org/sioc/ns#
comment	An Item is something which can be in a Container. (en)
disjointWith	Containerhttp://rdfs.org/sioc/ns#Container Spacehttp://rdfs.org/sioc/ns#Space Rolehttp://rdfs.org/sioc/ns#Role Usergrouphttp://rdfs.org/sioc/ns#Usergroup User Accounthttp://rdfs.org/sioc/ns#UserAccount
described by	proxy:entity/http/rdfs.org/sioc/nshttp://kingsley.idehen.net/about/id/entity/http/rdfs.org/sioc/ns

Property	Value
domain	has containerhttp://rdfs.org/sioc/ns#has_container addressed tohttp://rdfs.org/sioc/ns#addressed_to embeds knowledgehttp://rdfs.org/sioc/ns#embeds_knowledge abouthttp://rdfs.org/sioc/ns#about attachmenthttp://rdfs.org/sioc/ns#attachment contenthttp://rdfs.org/sioc/ns#content earlier versionhttp://rdfs.org/sioc/ns#earlier_version later versionhttp://rdfs.org/sioc/ns#later_version has discussionhttp://rdfs.org/sioc/ns#has_discussion has replyhttp://rdfs.org/sioc/ns#has_reply reply ofhttp://rdfs.org/sioc/ns#reply_of latest versionhttp://rdfs.org/sioc/ns#latest_version next by datehttp://rdfs.org/sioc/ns#next_by_date previous by datehttp://rdfs.org/sioc/ns#previous_by_date next versionhttp://rdfs.org/sioc/ns#next_version previous versionhttp://rdfs.org/sioc/ns#previous_version siblinghttp://rdfs.org/sioc/ns#sibling delivered athttp://rdfs.org/sioc/ns#delivered_at generatorhttp://rdfs.org/sioc/ns#generator mentionshttp://rdfs.org/sioc/ns#mentions read athttp://rdfs.org/sioc/ns#read_at respond tohttp://rdfs.org/sioc/ns#respond_to shared byhttp://rdfs.org/sioc/ns#shared_by
range	container ofhttp://rdfs.org/sioc/ns#container_of earlier versionhttp://rdfs.org/sioc/ns#earlier_version later versionhttp://rdfs.org/sioc/ns#later_version has replyhttp://rdfs.org/sioc/ns#has_reply reply ofhttp://rdfs.org/sioc/ns#reply_of latest versionhttp://rdfs.org/sioc/ns#latest_version next by datehttp://rdfs.org/sioc/ns#next_by_date previous by datehttp://rdfs.org/sioc/ns#previous_by_date next versionhttp://rdfs.org/sioc/ns#next_version previous versionhttp://rdfs.org/sioc/ns#previous_version siblinghttp://rdfs.org/sioc/ns#sibling discussion ofhttp://rdfs.org/sioc/ns#discussion_of
subClassOf	Posthttp://rdfs.org/sioc/ns#Post
disjointWith	Communityhttp://rdfs.org/sioc/ns#Community Containerhttp://rdfs.org/sioc/ns#Container Spacehttp://rdfs.org/sioc/ns#Space Rolehttp://rdfs.org/sioc/ns#Role Userhttp://rdfs.org/sioc/ns#User Usergrouphttp://rdfs.org/sioc/ns#Usergroup User Accounthttp://rdfs.org/sioc/ns#UserAccount
topic	http://rdfs.org/sioc/nshttp://rdfs.org/sioc/ns